Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

relation summary #911

Merged
merged 1 commit into from
Dec 2, 2024
Merged

relation summary #911

merged 1 commit into from
Dec 2, 2024

Conversation

ohad-starkware
Copy link
Collaborator

No description provided.

@reviewable-StarkWare
Copy link

This change is Reviewable

Copy link
Collaborator Author

ohad-starkware commented Nov 28, 2024

This stack of pull requests is managed by Graphite. Learn more about stacking.

@ohad-starkware ohad-starkware mentioned this pull request Nov 28, 2024
@ohad-starkware ohad-starkware mentioned this pull request Nov 28, 2024
@ohad-starkware ohad-starkware self-assigned this Nov 28, 2024
@codecov-commenter
Copy link

codecov-commenter commented Nov 28, 2024

Codecov Report

Attention: Patch coverage is 0% with 29 lines in your changes missing coverage. Please review.

Project coverage is 90.55%. Comparing base (e21f74f) to head (1400ec6).

Files with missing lines Patch % Lines
...rover/src/constraint_framework/relation_tracker.rs 0.00% 29 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##              dev     #911      +/-   ##
==========================================
- Coverage   90.74%   90.55%   -0.20%     
==========================================
  Files          94       94              
  Lines       13549    13578      +29     
  Branches    13549    13578      +29     
==========================================
  Hits        12295    12295              
- Misses       1140     1169      +29     
  Partials      114      114              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Performance Alert ⚠️

Possible performance regression was detected for benchmark.
Benchmark result of this commit is worse than the previous benchmark result exceeding threshold 2.

Benchmark suite Current: 1400ec6 Previous: cd8b37b Ratio
merkle throughput/simd merkle 27658225 ns/iter (± 670855) 13712527 ns/iter (± 579195) 2.02

This comment was automatically generated by workflow using github-action-benchmark.

CC: @shaharsamocha7

Copy link
Contributor

@Alon-Ti Alon-Ti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

:lgtm: with minor pondering

Reviewed 1 of 1 files at r1, all commit messages.
Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @ohad-starkware)


crates/prover/src/constraint_framework/relation_tracker.rs line 192 at r1 (raw file):

}

type RelationInfo = (String, Vec<(Vec<M31>, M31)>);

Is there a non-destructive way to unify this, RelationEntry and RelationTrackerEntry?

Copy link
Collaborator Author

@ohad-starkware ohad-starkware left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @Alon-Ti)


crates/prover/src/constraint_framework/relation_tracker.rs line 192 at r1 (raw file):

Previously, Alon-Ti wrote…

Is there a non-destructive way to unify this, RelationEntry and RelationTrackerEntry?

the relation tracker could sit with the logup stuff under some "lookup_utils" folder in the constraint(air) framework

Copy link
Collaborator Author

ohad-starkware commented Dec 2, 2024

Merge activity

  • Dec 2, 4:45 AM EST: A user started a stack merge that includes this pull request via Graphite.
  • Dec 2, 4:47 AM EST: Graphite rebased this pull request as part of a merge.
  • Dec 2, 4:50 AM EST: A user merged this pull request with Graphite.

@ohad-starkware ohad-starkware changed the base branch from ohad/relationeval to graphite-base/911 December 2, 2024 09:45
@ohad-starkware ohad-starkware changed the base branch from graphite-base/911 to dev December 2, 2024 09:45
@ohad-starkware ohad-starkware merged commit f7de614 into dev Dec 2, 2024
16 of 19 checks passed
@ohad-starkware
Copy link
Collaborator Author

crates/prover/src/constraint_framework/relation_tracker.rs line 192 at r1 (raw file):

Previously, ohad-starkware (Ohad) wrote…

the relation tracker could sit with the logup stuff under some "lookup_utils" folder in the constraint(air) framework

oh if you meant unifying to a single struct then no, this represents multiple entries that are not even from the same trace

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants